[pull] main from expo:main - #1156

… missing (#48840)

…49009)

# Why

Follow-up to #48816, where we agreed to handle this in a separate PR.

Sentence case is an English orthography rule. Japanese has no letter
case, so `HeadingCase` can only ever fire on a Japanese heading that
happens to open with an ASCII identifier — and Japanese headings are
verb-final, so they routinely open with the object: a file name, a job
type, a CLI flag, an acronym.

In #48816 that produced ten headings where applying the rule renamed
real files — `### Hello.yml ファイルを追加する` above instructions to create a
file named **hello.yml** — and the resolution was six new exception
patterns.

The pattern repeats on every batch of translated pages, and the
exceptions it needs are wide enough to reach the English docs.
Translating the Development process guides needs another twelve: `app
config`, `assetlinks.json`, `babel-plugin`, `config plugin`, `direnv`,
`gradle`, `jest`, `monorepo`, `peerDependencies`, `react-native-config`,
`source-map-explorer`, `DOM`, and `ref`. That last one has to be
`.*\brefs?\b.*` to cover `## ref を渡す`, which exempts every English
heading containing "ref" or "refs" as a side effect. So each new
translated page quietly buys down the check for pages the rule was
written for.

# How

Scope the rule out of `pages/ja/**` in `.vale.ini`, the same way
`README.md` already opts out of `Prerequisites` and `KeyboardShortcuts`.

```ini
[**/pages/ja/**]
expo-docs.HeadingCase = NO
```

`HeadingCase.yml` is untouched — the six patterns added in #48816 stay
where they are rather than being cleaned up here, so this PR is six
lines and reversible on its own.

The other 24 styles still apply to the translations.

# Test Plan

- `pnpm lint-prose` — clean, 1592 files.
- Confirmed the exemption is scoped to this one rule, not to the
directory. Added a merge conflict marker to
`pages/ja/tutorial/screenshot.mdx` and `expo-docs.MergeConflictMarkers`
still fired; added `## console ログを削除する` to a Japanese page and
`HeadingCase` stayed quiet.
- Confirmed English pages are unaffected: this PR changes no style file,
and the run above covers the full `pages` tree.

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
-->

- [ ] I added a `changelog.md` entry and rebuilt the package sources
according to [this short
guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
- [x] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)

---------

Co-authored-by: Aman Mittal <amandeepmittal@live.com>

Added a note about downloading the Expo Go APK if the latest version is
not yet available on the Google Play Store.

# Why

This change provides an alternative way to install Expo Go on Android
when the latest version is not yet available on the Google Play Store.

# How

Added a note to the environment setup documentation with a link to the
Expo Go download page, where users can download the APK.

# Test Plan

Reviewed the documentation change to ensure the wording follows the Expo
Documentation Writing Style Guide and that the download link points to
the official Expo Go download page.

# Checklist

* [ ] I added a `changelog.md` entry and rebuilt the package sources
according to [[this short
guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)
* [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
* [x] Conforms with the [[Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)

---------

Co-authored-by: Aman Mittal <amandeepmittal@live.com>

# Why

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

Supersedes #48145 and
#48144.

Regenerate React Navigation options.


# Test Plan

<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

N/A

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
-->

- [ ] I added a `changelog.md` entry and rebuilt the package sources
according to [this short
guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)

<!-- disable:changelog-checks -->

# Why

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

Fix ENG-25993

# How

<!--
How did you build this feature or fix this bug and why?
-->

Fix the Stack.SearchBar onChangeText example.

# Test Plan

<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

Proofread.

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
-->

- [ ] I added a `changelog.md` entry and rebuilt the package sources
according to [this short
guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)

…49014)

# Why

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->


<img width="1552" height="416" alt="CleanShot 2026-08-17 at 14 04 33@2x"
src="https://github.com/user-attachments/assets/65c43142-0c40-4d16-860b-a87762ceb0a3"
/>

# How

<!--
How did you build this feature or fix this bug and why?
-->

Fix the script to strip React Navigation layout markup from generated
options.

# Test Plan

<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

See the build step in CI of this PR.

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
-->

- [ ] I added a `changelog.md` entry and rebuilt the package sources
according to [this short
guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build
(eg: updated a module plugin).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)